Dynomotion

Group: DynoMotion Message: 5184 From: frank_19_88 Date: 6/11/2012
Subject: Buffer starved
Hi TK,

When I try to cut an circle within mach3 (with the mill plug-in)

I got very often an error 'Dynomotion Buffer starved' when the circle is exact
half way. (when the machine is at x0 again)

When I change my 0-point I got the same error at exact the same point.

I did try to increase the 'Buffer at mach3,settings, plugin, dynomotion' But
without any result.

Some time's when the speed is higher or some time when speed is lower I don't
receive the error.


Within the 5th thread I am running an loop forever to watch software limits and
to correct my resolver input offset. Maybe it is to big?

I have an PC with win XP about 1 Ghz.


Do you have any idea what is going wrong?

Frank
Group: DynoMotion Message: 5186 From: Tom Kerekes Date: 6/11/2012
Subject: Re: Buffer starved
Hi Frank,
 
Not sure why that would happen.  What version of the KMotion are you using?
 
What are your Mach3 "tuning" parameters?  Axis resolutions?  Maybe post your XML file for us and with a Gcode fragment.
 
What user threads are doing or how big they are shouldn't have any effect.  How many are running does steal CPU time from processing motion segments but should not be a problem.
 
Regards
TK

Group: DynoMotion Message: 5188 From: Fouijar Date: 6/11/2012
Subject: Re: Buffer starved
Hi Franck,

I had motion buffer troubles, not as systematic as your issue but occurring in similar motions. My problem was a following error occurring at transient, accelerations phases, especially in circular pockets and rapids.

I started like that:
- Increase the following error to check if this was the origin of motion buffer issue.
- Then I better tuned my system to increase the bandwidth and margins.
- Set my following error as tight as possible and check under test runs.

I did a lot of testing before getting thinks as I wanted them but now it's fine and fully functional under fast and heavy cutting conditions.

This is maybe not your situation but I hope this help,

Jerome


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Frank,
>  
> Not sure why that would happen.  What version of the KMotion are you using?
>  
> What are your Mach3 "tuning" parameters?  Axis resolutions?  Maybe post your XML file for us and with a Gcode fragment.
>  
> What user threads are doing or how big they are shouldn't have any effect.  How many are running does steal CPU time from processing motion segments but should not be a problem.
>  
> Regards
> TK
>
> From: frank_19_88 <frank_19_88@...>
> To: DynoMotion@yahoogroups.com
> Sent: Monday, June 11, 2012 9:29 AM
> Subject: [DynoMotion] Buffer starved
>
>
>  
> Hi TK,
>
> When I try to cut an circle within mach3 (with the mill plug-in)
>
> I got very often an error 'Dynomotion Buffer starved' when the circle is exact
> half way. (when the machine is at x0 again)
>
> When I change my 0-point I got the same error at exact the same point.
>
> I did try to increase the 'Buffer at mach3,settings, plugin, dynomotion' But
> without any result.
>
> Some time's when the speed is higher or some time when speed is lower I don't
> receive the error.
>
> Within the 5th thread I am running an loop forever to watch software limits and
> to correct my resolver input offset. Maybe it is to big?
>
> I have an PC with win XP about 1 Ghz.
>
> Do you have any idea what is going wrong?
>
> Frank
>
Group: DynoMotion Message: 5189 From: Tom Kerekes Date: 6/11/2012
Subject: Re: Buffer starved
Hi Frank,
 
I see from your private email that you are using V4.28.  There was a bug in the Mach3 plugin related to the transition from points on a circle (or curved path) near -180 degrees to points near +180 degrees.  This was fixed in Version 4.29.
 
Please try V4.29 to see if it solves the problem.
 
Regards
TK